Hello, These days when I try to open a shared folder in other machines(including XP, Vista, 7, Server 2003/2008) from my own Windows 7 Ultimate pc, I get a Network Error dialog saying: Windows cannot access \\machine\sharedfolder, error code 0x80004005, unspecified error. It aslo failed with IP. And I have disable the Firewall But the other XP, Vista, Server 2003 and Server 2008 machines can reach each other and they even can open the shared fodler from my Windows 7. It's too strange. Maybe you can give me some useful suggestion. Thanks. Xiaofeng @//+++all the context of the issue Hope Helpful | http://www.leoworks.net

Hi Dale Thanks for your response. Unfortunately, it's not fixed after disabling IP6. I take 0xffffffff as value of DisabledComponents to disable all the IP6 components.@//+++all the context of the issue Hope Helpful | http://www.leoworks.net

Hi Dale Thanks for your response. Unfortunately, it's not fixed after disabling IP6. I take 0xffffffff as value of DisabledComponents to disable all the IP6 components. @//+++all the context of the issue Hope Helpful | http://www.leoworks.net Did you ensure file and folder sharing in xp and vista is enable and there's no third party firewall on this two rig? I suggest you to map using it's IP as well as host name of the xp and vista machine Use the following method if you're mapping through IP \\192.168.X.XXX or alternatively if through host name \\Wang=PC First of all you need to find out the exact IP or host name of the xp and vista rig before you could mapped it from the win 7 rig

Hi Daniel I have disabled all the firewall for the test. Neither IP nor host name can be avaiable. As I said above, only one Window 7 can not access shared resources from other machines(xp, vista, server 2003, server 2008), but other machines can access each other, they also can access shared resouces from the Windows 7. It seems this Windows 7 guy locks himself in the room but seeing others get in and go out. too strange. Thanks. @//+++all the context of the issue Hope Helpful | http://www.leoworks.net

I have exactly the same problem with my Windows 7 Enterpise x64 on my laptop. It happened sometimes around last week, and it worked fine before that. I also have this strange Microsoft Virtual WiFi Miniport Adapter, but disabling, uninstalling it, or changing its settings - doesnt help. I tried disbling IPv6 - it doesnt help either. Any help will be really appreciated. Thanks

I really need some help here. Any suggestions?

I had the exact same problem as descibed. For some reason I could no longer connect to my NAS drive via my network share or by typing \\machine\share in windows explorer. Then I remembered that I had installed PHP5, apache, a web deployment tool and some other additional tools to run Wordpress locally. The troubles started around that time. I used system restore to go back before the newly installed programs. That solved it for me. See this site for instructions on how to use system restore: http://www.sevenforums.com/tutorials/700-system-restore.html @axlns - The problem is probably not caused by windows update because I just updated my system (windows 7 ultimate - 32bit) to all latest updates and I can still connect to my network shares.

Had similar issues as described in 'Lyndon's Mobile' post above. NAS (\\192.168.1.xx\Public) accessible from laptop and mac mini, desktop system refuses to connect throwing 0x80004005 error. Both the laptop and desktop system are win7 home premium. Following the suggestion from 'axlns' post 'Client for Microsoft Networks' was not installed on the desktop system network adapter. Installing it fixed the issue and NAS is now accessible to all three systems. It was working on all three platforms in the past, I'm not sure how it 'broke'. About the only difference between the laptop and desktop systems has been the installation of HP networked printer drivers. As a test the same drivers were installed on the laptop and shutdown/restart preformed. NAS and printer are working fine so I haven’t got a clue when or how the 'Client for Microsoft Networks' got uninstalled on the desktop system. Something else ‘changed’ between 11/27/2010 and 10/17/2010, my last desktop backup date to the NAS.

I too, am having the same problems WIH7 ULT, 64bit. I can open the web brower for the webpage setup but cannot access the drive, no matter what I try. Am using a work group setup.Another laptop and two desktops have no issues. Just this laptop. The problem just appeared. I tried reverting without success.William R. Johnson

I had a similar problem as axlns and followed the steps advised and now my windows 7 laptop can "see" xp and earlier computers on the network. the solution was to add back clients for microsoft network which for some reason was not there in the wireless adapter properties. adoor

Same problem with a MSI Wind Notebook. I was looking for anything else but I could't see that the "Client for Microsoft Networks" didn't appear in the properties fo the network adapter. Now, I wonder why it dissapeared in the first place! Thank you axlns anyway

Mine was also the client for MS networks had been removed. Added this back and was able to browse. Have no clue how it was removed, but it is better now.

Hi, Can you pls tell me how to reinstall the client for microsoft networks. I am having the same problem!

Any other solution on that problem? I tried all the mentioned things, but nothing helped. Thanks, S.

I finally fixed my problems. It turns out that my network adapter somehow loosed component called "Client for Microsoft Networks", not sure how that happened, I certainly did not removed it manually. Anyway, I have installed it back, rebooted, and voila, everything started working again! You are my hero! I have been searching online for two days and going down the path of virus removal, registry edits, updates, firewalls and everything else under the sun! Added the Client for Microsoft Networks and I'm back up and running on my network. No idea how that was ever removed?! I had been sharing on the network with no problem for a couple months and then this randomly came up. Thanks for the weird fix that actually fixed it!

codenamemessiah - go to your network connections, right click and go to Properties. In there, click 'Install' and choose 'Client' and you'll see the option there. Hope that helps.

THKS, It works for me too, I don't know how to disapear it, but now works. Thanks.

This will only work if you are trying to access computer from a different domain or workgroup. Under your NIC, IPV4 propreties -> Advance -> DNS tab -> Append these DNS suffix(in order): -> add domain names or workgroup names from which you are trying to access the resources. I hope this helps.

I had the same problem and this work for me: http://www.ryanvictory.com/posts/automating-6to4-adapter-removal-in-windows/

Had same problem, but nothing here worked. Oddly I could bring up a cmd window and dir \\shareip\share, I could even xcopy files from shares. I used autoruns and eventually figured out that my NetworkProvider order was incorrect. the "LanmanWorkstation" entry had been chopped in half. Modifying the entry restored functionality instantly. Registry key... HKLM\SYSTEM\CurrentControlSet\Control\NetworkProvider\Order = (REG_SZ) "RDPNP,LanmanWorkstation"

Hello, These days when I try to open a shared folder in other machines(including XP, Vista, 7, Server 2003/2008) from my own Windows 7 Ultimate pc, I get a Network Error dialog saying: Windows cannot access \\machine\sharedfolder, error code 0x80004005, unspecified error. It aslo failed with IP. And I have disable the Firewall But the other XP, Vista, Server 2003 and Server 2008 machines can reach each other and they even can open the shared fodler from my Windows 7. It's too strange. Maybe you can give me some useful suggestion. Thanks. Xiaofeng @//+++all the context of the issue Hope Helpful | http://www.leoworks.net

Thank you, mcgoober. You set me on the right path. I discovered: HKLM\SYSTEM\CurrentControlSet\Control\NetworkProvider\Order - Provider Order and HKLM\SYSTEM\CurrentControlSet\Control\NetworkProvider\HWOrder - Provider Order values were set to LanmanWorkstation,RDPNP in both string values referenced above. I changed these both to RDPNP,LanmanWorkstation and I was then able to connect without a problem.

McGoober, you saved my arse. I had a working Win 7 Pro computer on a domain and lost access to the server and mapped drives. With your comments, I determined that a Lotus update I performed earlier today to support a feature called "single user logon" wiped out the contents of the HKLM\SYSTEM\CurrentControlSet\Control\NetworkProvider\Order key with the exception of one entry the update made. I was able to use a working Win 7 Pro workstation to re-enter the correct values and am now connected to server with all mapped drives back. Thanks.

This worked for me http://www.orison.biz/blogs/chall3ng3r/?p=2932